You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.
cmd notification-hub authorization-rule list-keys update parameter resource_group_name: updated property name from resource_group_name to resource_group
cmd notification-hub authorization-rule regenerate-keys update parameter resource_group_name: updated property name from resource_group_name to resource_group
cmd notification-hub namespace authorization-rule create update parameter resource_group_name: updated property name from resource_group_name to resource_group
cmd notification-hub namespace authorization-rule delete update parameter resource_group_name: updated property name from resource_group_name to resource_group
notification-hub namespace authorization-rule list
cmd notification-hub namespace authorization-rule list update parameter resource_group_name: updated property name from resource_group_name to resource_group
cmd notification-hub namespace authorization-rule list-keys update parameter resource_group_name: updated property name from resource_group_name to resource_group
cmd notification-hub namespace authorization-rule regenerate-keys update parameter resource_group_name: updated property name from resource_group_name to resource_group
notification-hub namespace authorization-rule show
cmd notification-hub namespace authorization-rule show update parameter resource_group_name: updated property name from resource_group_name to resource_group
Hi @Jing-song,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az notification-hub
AAZ model: Azure/aaz#243
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally?For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.